Server workload assignment based on known update/security vulnerabilities

ABSTRACT

Systems and computer program products to perform an operation comprising determining that a first component of a first compute node violates a compliance rule, wherein the first compute node executes a plurality of workloads and is of a plurality of compute nodes in a computing cluster, performing a predefined operation to defer need to apply a software update configured to correct the violation of the compliance rule by the first component of the first compute node, and executing, by the first compute node, at least one of the plurality of workloads without applying the software update.

BACKGROUND

The present invention relates to computing systems, and morespecifically, to assigning workloads based on known updates and/orsecurity vulnerabilities.

Software updates are frequently applied to computing devices for avariety of reasons, including fixing errors, addressing securityvulnerabilities, and keeping software up to date. However, softwareupdates may be distributed at times where the computing systems cannotapply the software updates. For example, a system may be in production,and services provided by the system cannot be taken offline to apply theupdate. Similarly, a system may not have the correct network connectionto download the update. As another example, the update might be forunneeded software. Software updates are conventionally applied as soonas possible, in spite of the risks that may arise when doing so.

SUMMARY

Embodiments disclosed herein include systems and computer programproducts to perform an operation comprising determining that a firstcomponent on a first compute node, of a plurality of compute nodes in acomputing cluster, violates a compliance rule, wherein the first computenode executes a plurality of workloads, wherein a software update isconfigured to correct the violation of the compliance rule by the firstcomponent of the first compute node, performing a predefined operationto defer applying the software update for a period of time, andexecuting, by the first compute node, at least one of the plurality ofworkloads during the period time.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 illustrates a system configured to assign workloads based onknown updates and/or security vulnerabilities, according to oneembodiment.

FIG. 2 illustrates a method to assign workloads based on softwareupdates, according to one embodiment.

FIG. 3 illustrates a method to perform a predefined operation to deferthe need to apply a software update, according to one embodiment.

FIGS. 4A-4B illustrate techniques to assign workloads based on softwareupdates, according to various embodiments.

FIG. 5 depicts a cloud computing node according to one embodiment.

FIG. 6 depicts a cloud computing environment according to oneembodiment.

FIG. 7 depicts abstraction model layers according to one embodiment.

DETAILED DESCRIPTION

Embodiments disclosed herein provide techniques to defer (or completelyavoid) the need to apply software updates to computing systems. Insteadof automatically applying a software update to a computing system,embodiments disclosed herein attempt to uninstall software, reconfigureworkloads, or shift workloads to avoid the software at risk, and unableto negatively affect the computing system. Doing so may prolong theuptime of a system and avoid system downtime needed to apply softwareupdates.

For example, developers may release an update that fixes securityvulnerabilities of software package A. Compute node X in a computecluster may execute a version of software package A that has not beenupdated to fix the security vulnerability. However, in order to applythe software update, compute node X (or a virtual machine hosting thesoftware to be updated) may need to be restarted, which may takecritical services offline. Instead of taking down compute node X,embodiments disclosed herein may defer (or obviate) the need to applythe update to software package A. For example and without limitation,administrators or management applications may uninstall software packageA from compute node X in scenarios where software package A is notneeded (or not used) on compute node X. Similarly, in anotherembodiment, the software update to software package A may be applied tocompute node Y. Once software package A is updated on compute node Y,embodiments may migrate the services/workloads of compute node X tocompute node Y. In still another embodiment, compute node Y may beprohibited or prevented from executing software package A, and willtherefore not need to be updated before migrating services/workloadsfrom compute node X to compute node Y. In another embodiment, workloadsthat are scheduled for deployment on compute node X may be rescheduledto accommodate the installation of the software update to softwarepackage A on compute node X. In each of these examples, installation ofthe update to software package A on compute node X may be deferred orcompletely rendered unnecessary, as compute node X will not use theaffected software package X.

As used herein, a software update (or upgrade) may include any type ofsoftware update, regardless of the purpose of the software update. Forexample, the software update may fix or close security risks and/orvulnerabilities, correct runtime errors, correct dropped connections, orupgrade out of date software versions to a more current version. Thesoftware updates may target any type of computing element, includingcomputing hardware, firmware, and/or software.

FIG. 1 illustrates a system 100 configured to assign workloads based onknown updates and/or security vulnerabilities, according to oneembodiment. The networked system 100 includes a computer 102. Thecomputer 102 may also be connected to other computers via a network 130.In at least one embodiment, the system 100 depicts a computing clustercomprising the computer 102 and a plurality of compute nodes 150. Ingeneral, the network 130 may be a telecommunications network and/or awide area network (WAN). In a particular embodiment, the network 130 isthe Internet.

The computer 102 generally includes a processor 104 which obtainsinstructions and data via a bus 120 from a memory 106 and/or a storage108. The computer 102 may also include one or more network interfacedevices 118, input devices 122, and output devices 124 connected to thebus 120. The computer 102 is generally under the control of an operatingsystem (not shown). Examples of operating systems include the UNIXoperating system, versions of the Microsoft Windows operating system,and distributions of the Linux operating system. (UNIX is a registeredtrademark of The Open Group in the United States and other countries.Microsoft and Windows are trademarks of Microsoft Corporation in theUnited States, other countries, or both. Linux is a registered trademarkof Linus Torvalds in the United States, other countries, or both.) Moregenerally, any operating system supporting the functions disclosedherein may be used. The processor 104 is a programmable logic devicethat performs instruction, logic, and mathematical processing, and maybe representative of one or more CPUs. The network interface device 118may be any type of network communications device allowing the computer102 to communicate with other computers via the network 130.

The storage 108 is representative of hard-disk drives, solid statedrives, flash memory devices, optical media and the like. Generally, thestorage 108 stores application programs and data for use by the computer102. In addition, the memory 106 and the storage 108 may be consideredto include memory physically located elsewhere; for example, on anothercomputer coupled to the computer 102 via the bus 120.

The input device 122 may be any device for providing input to thecomputer 102. For example, a keyboard and/or a mouse may be used. Theinput device 122 represents a wide variety of input devices, includingkeyboards, mice, controllers, and so on. Furthermore, the input device122 may include a set of buttons, switches or other physical devicemechanisms for controlling the computer 102. The output device 124 mayinclude output devices such as monitors, touch screen displays, and soon.

As shown, the memory 106 contains the management application 112, whichis an application generally configured to intelligently manage workloadson the compute nodes 150 based on known software updates. In addition,the management application 112 generally manages the deployment andmanagement of virtual machines 113 and their workloads 114 on thecompute nodes 150. One example of such a management application is xCAT(Extreme Cloud Administration Toolkit), developed by IBM, which isconfigured to manage the compute nodes 150 by interfacing with aplurality of different hypervisors 121. Generally, a hypervisor 121creates, manages, and runs virtual machines 113 on the compute nodes150. The virtual machines 113 may execute any type of software,including the workloads 114. The workloads 114 may be services orcollections of code that can be executed.

As shown, the storage 108 contains the compliance rules 116 and softwareupdates 117. The software updates 117 may include any type of updatesfor software and/or firmware. For example, the software updates 117 mayinclude patches, fixes, new versions of software, and the like. Thesoftware updates 117 may be enriched with metadata specifying targets(hardware, software, and/or firmware) and other attributes of eachupdate. The compliance rules 116 may include different rules forsoftware and/or hardware components of the compute nodes 150. Themanagement application 112 may automatically generate compliance rules116 responsive to receiving indications of software updates 117,security vulnerabilities, and the like. In other embodiments, thecompliance rules 116 may be defined by a user, such as a systemadministrator.

For example, the compliance rules 116 may specify the most currentversions of software and/or firmware. If the management application 112determines that a compute node 150 is not running the most currentversion of the software, the management application 112 may performpredefined operations to delay or obviate the need to install an updateto the software so that the compliance rules 116 are satisfied. Asanother example, the compliance rules 116 may specify securityvulnerabilities, threats, loopholes, and the like, which may require asoftware update 117 to be fixed. If a given compute node 150 has notreceived the corresponding software update 117, the managementapplication 112 may determine that the compute node 150 violates thecompliance rule 116, and the management application 112 may attempt toorchestrate installation of the software update according to thetechniques described herein. As another example, the compliance rules116 may identify hardware components that are not acceptable for use inthe compute nodes 150. For example, a network adapter may be known tocause data corruption. If a compute node 150 includes the offendingnetwork adapter, the management application 112 may disable theoffending network adapter so that it does not corrupt any more data. Inaddition, if an update for the network adapter is in the softwareupdates 117, the management application 112 may adjust the deployment ofvirtual machines 113 and/or workloads 114 such that the offendingnetwork adapter is not used until the software update 117 is applied.Generally, the compliance rules 116 may specify any number and type ofrules that are associated with one or more software updates 117. Thecompliance rules 116 may also specify corresponding operations that themanagement application 112 may perform to cause the compute nodes 150 tocome into compliance with a given compliance rule 116.

For example, one compliance rule 116 may specify that version 1.0 of asoftware compiler has a security vulnerability which may be fixed byupdating the compiler to version 1.1 through an update stored in thesoftware updates 117. The management application 112 may then determinethat a first virtual machine 113 on first compute node 150 includesversion 1.0 of the compiler. In response to the violation of thecompliance rule 116 related to the compiler, the management application112 may perform a predefined operation to delay and/or obviate the needto update the compiler. In one embodiment, the management application112 may identify one or more enumerated operations associated with thecompliance rule 116. In another embodiment, the management application112 includes a set of predefined operations that may be applied acrossall types of rule violations. For example, the first virtual machine 113may execute a first, second, and third workload 114, where only thefirst workload 114 utilizes version 1.0 of the compiler. In such ascenario, the management application 112 may move the first workload 114to a second compute node 150, where the second compute node 150 includesversion 1.1 of the compiler. In at least one embodiment, the managementapplication 112 may interface with the hypervisor 121 managing the firstvirtual machine to move the first workload 114 to a different computenode. The management application 112 may also allow the second and thirdworkloads 114 to run unmodified, as the second and third workloads 114do not use the offending compiler, and the risks associated with version1.0 of the compiler may be avoided without requiring the update toversion 1.1 of the compiler. Generally, the management application 112may perform any predefined operation to address the violation of acompliance rule 116. For example, if version 1.0 of the compiler is notused on a given system, the management application 112 may uninstallversion 1.0 of the compiler, and store an indication in the storage 108to reinstall version 1.1 of the compiler at a later time.

In at least one embodiment, the hypervisors 121 may incorporate thefunctionality of the management application 112 that assigns serverworkload based on software updates and/or security vulnerabilities. Forexample, in one example environment, the computer 102 may also host ahypervisor 121 that manages a set of virtual machines 113 and associatedworkloads 114 in the memory 106. In such environments, the managementapplication 112 may not be required to interface between differentvirtualized environments (and their respective hypervisors 121).Therefore, the hypervisor 121 may identify software updates 117 forinstallation on the computer 102, and perform predefined operations todelay and/or obviate the need to install the software updates on thecomputer 102.

FIG. 2 illustrates a method 200 to assign workloads based on softwareupdates, according to one embodiment. Generally, the steps of the method200 provide techniques to defer or eliminate the need to installsoftware updates upon receipt. As shown, the method 200 begins at step210, where the management application 112 may receive an indication of asoftware update, security vulnerability, or other required softwareupgrade in the software updates 117. In at least one embodiment, a usermay provide the indication. In response, the management application 112may reference metadata associated with the software updates 117 toidentify a component of the computing system targeted by the softwareupdate 117. For example, a first software update 117 may target asecurity vulnerability in an operating system, while a second softwareupdate 117 may target flawed firmware of a hardware component. At step220, the management application 112 may determine that a first computenode violates a compliance rule related to the software update (orsecurity vulnerability). For example, if a critical security fix isreceived for an operating system, the management application 112 maydetermine that the operating system of a first virtual machine 113executing on the first compute node has not been updated based onmetadata associated with the operating system provided by the hypervisor121 managing the first virtual machine. In at least one embodiment, themanagement application 112 may maintain a database of all installedsoftware and hardware components of each compute node 150 in the storage108, thereby facilitating the determination as to which componentsviolate compliance rules 116.

At step 230, described in greater detail with reference to FIG. 3, themanagement application 112 may perform a predefined operation to defer(and/or eliminate) the need to apply the software update to the firstcompute node. Generally, the management application 112 may perform anyset of operations to ensure that the offending hardware and/or softwareis not used. For example, continuing with the previous example, if theoperating system security fix is the required software update 117, themanagement application 112 may migrate workloads 114 associated with thefirst virtual machine 113 on the first compute node 150 to a virtualmachine 113 on a second compute node. If, however, a second virtualmachine 113 is not affected, the management application 112 may allowthe second virtual machine 113 to continue execution on the firstcompute node 150 while the first virtual machine 113 is updated andrebooted. At step 240, the first compute node may continue executing atleast one workload 114 without applying the software update. Forexample, a first workload 114 may be migrated to a second compute node150 because the first workload 114 uses a component of the first computenode 150 that is targeted by a software update. However, a secondworkload 114 executing on the first compute node 150 may not bemodified, as the second workload 114 may not use the component of thefirst compute node 150 that is targeted by the software update. At step250, the management application 112 may optionally apply the softwareupdate to the first compute node.

FIG. 3 illustrates a method 300 corresponding to step 230 to perform apredefined operation to defer the need to apply a software update,according to one embodiment. Generally, the method 300 includes one ormore operations that the management application 112 may perform to deferor eliminate the need to apply a software update. At step 310, themanagement application 112 may optionally alter a workload 114 to notuse an offending component. For example, if a workload 114 uses asoftware package, compiler, network port, or operating system componentthat is the target of a software update, the management application 112may provide a suitable alternate component that is determined to notviolate any compliance rules 116. At step 320, the managementapplication 112 may optionally move one or more workloads to a differentcompute node. For example, if the second compute node is not affected,the workload may be moved to the second compute node, allowing theworkloads to run while the software update is applied to the firstcompute node. At step 330, the management application 112 may optionallyinstall the software update 117 to a second compute node, and moveaffected workloads from the first compute node to the second computenode. At step 340, the management application 112 may optionallyuninstall the software targeted by a software update 117, and maintain arecord to re-install the updated software at a later time (such as aftera system reboot). At step 350, the management application 112 mayoptionally alter the schedules and/or targets (e.g., compute nodes) ofworkloads around prioritization of software updates. For example, anadministrator may define a daily window of time for applying softwareupdates, such as from 3 AM-4 AM. Therefore, workloads that may beaffected can be scheduled to run around the updates.

FIG. 4A illustrates techniques to assign workloads based on softwareupdates, according one embodiment. As shown, FIG. 4A depicts two computenodes, namely compute nodes 150 ₁ and 150 ₂, which execute virtualmachines 113 ₁ and 113 ₂, respectively. Virtual machine 113 ₁ executesworkloads 114 ₁ and 114 ₂, while virtual machine 113 ₂ executes workload114 ₃ and workload 114 ₄. As shown, virtual machine 113 ₁ is targeted bya security update which has not been installed. The security update maybe any type of update, such as a patch to close an open securityloophole. The management application 112 may determine that workload 114₁ does not use the component targeted by the uninstalled securityupdate, while workload 114 ₂ does use the component affected by theuninstalled security update. As shown, no updates are ready forinstallation on compute node 150 ₂. As such, the management application112 may modify the configuration of compute node 150 ₁ to delay orobviate the need to install the security patch on compute node 150 ₁.

FIG. 4B reflects compute nodes 150 ₁, 150 ₂ after the managementapplication 112 has caused the migration of workload 114 ₂ to virtualmachine 113 ₂ of compute node 150 ₂. As shown, virtual machine 113 ₁ ofcompute node 150 ₁ continues to execute workload 114 ₁, but no longerexecutes 114 ₂. The security update is still available, but has not beeninstalled, allowing workload 114 ₁ to continue to execute. However,since workload 114 ₂ has been migrated to compute node 150 ₂, the riskof not installing the upgrade is minimized, as workload 114 ₁ does notuse the affected component that has not been addressed by the securityupdate. Advantageously, the security update may be installed at a latertime. As shown, virtual machine 113 ₂ now runs workloads 114 ₂, 114 ₃,and 114 ₄. However, in one embodiment, the management application 112may migrate one or both of workloads 114 ₃ and 114 ₄ to compute node 150₁ (assuming neither workload 114 ₃ nor workload 114 ₄ uses the affectedcomponent of compute node 150 ₁).

Advantageously, embodiments disclosed herein defer or completely obviatethe need to apply software updates. While software updates areconventionally applied immediately upon receipt, embodiments disclosedherein alter or move computing workloads to avoid the use of offendinghardware and/or software until the software update can be applied at alater time. Doing so provides increased uptime of key services andreduces overall downtime.

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

For convenience, the Detailed Description includes the followingdefinitions which have been derived from the “Draft NIST WorkingDefinition of Cloud Computing” by Peter Mell and Tim Grance, dated Oct.7, 2009, which is cited in an IDS filed herewith, and a copy of which isattached thereto.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as Follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as Follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as Follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 5, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 5, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnects (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via I/O interfaces22. Still yet, computer system/server 12 can communicate with one ormore networks such as a local area network (LAN), a general wide areanetwork (WAN), and/or a public network (e.g., the Internet) via networkadapter 20. As depicted, network adapter 20 communicates with the othercomponents of computer system/server 12 via bus 18. It should beunderstood that although not shown, other hardware and/or softwarecomponents could be used in conjunction with computer system/server 12.Examples, include, but are not limited to: microcode, device drivers,redundant processing units, external disk drive arrays, RAID systems,tape drives, and data archival storage systems, etc.

Referring now to FIG. 6, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 6 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 7, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 6) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 7 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes, in oneexample IBM® zSeries® systems; RISC (Reduced Instruction Set Computer)architecture based servers, in one example IBM pSeries® systems; IBMxSeries® systems; IBM BladeCenter® systems; storage devices; networksand networking components. Examples of software components includenetwork application server software, in one example IBM WebSphere®application server software; and database software, in one example IBMDB2® database software. (IBM, zSeries, pSeries, xSeries, BladeCenter,WebSphere, and DB2 are trademarks of International Business MachinesCorporation registered in many jurisdictions worldwide)

Virtualization layer 62 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer 64 may provide the functions describedbelow. Resource provisioning provides dynamic procurement of computingresources and other resources that are utilized to perform tasks withinthe cloud computing environment. Metering and Pricing provide costtracking as resources are utilized within the cloud computingenvironment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal provides access to the cloud computing environment forconsumers and system administrators. Service level management providescloud computing resource allocation and management such that requiredservice levels are met. Service Level Agreement (SLA) planning andfulfillment provide pre-arrangement for, and procurement of, cloudcomputing resources for which a future requirement is anticipated inaccordance with an SLA.

Workloads layer 66 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation; software development and lifecycle management; virtualclassroom education delivery; data analytics processing; transactionprocessing; and software updates.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

In the foregoing, reference is made to embodiments presented in thisdisclosure. However, the scope of the present disclosure is not limitedto specific described embodiments. Instead, any combination of therecited features and elements, whether related to different embodimentsor not, is contemplated to implement and practice contemplatedembodiments. Furthermore, although embodiments disclosed herein mayachieve advantages over other possible solutions or over the prior art,whether or not a particular advantage is achieved by a given embodimentis not limiting of the scope of the present disclosure. Thus, therecited aspects, features, embodiments and advantages are merelyillustrative and are not considered elements or limitations of theappended claims except where explicitly recited in a claim(s). Likewise,reference to “the invention” shall not be construed as a generalizationof any inventive subject matter disclosed herein and shall not beconsidered to be an element or limitation of the appended claims exceptwhere explicitly recited in a claim(s).

Aspects of the present invention may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects that may all generally bereferred to herein as a “circuit,” “module” or “system.”

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

While the foregoing is directed to embodiments of the present invention,other and further embodiments of the invention may be devised withoutdeparting from the basic scope thereof, and the scope thereof isdetermined by the claims that follow.

What is claimed is:
 1. A computing cluster, comprising: a plurality ofcompute nodes in a computing cluster, each of the compute nodescomprising at least one processor; and a management system comprisingone or more processors configured to manage the plurality of computenodes by performing an operation comprising: determining that a firstcomponent on a first compute node, of the plurality of compute nodes inthe computing cluster, violates a compliance rule, wherein the firstcompute node executes a plurality of workloads, wherein a softwareupdate is configured to correct the violation of the compliance rule bythe first component of the first compute node; identifying one or morepredefined operations associated with the compliance rule; andperforming the one or more predefined operations while deferringapplying the software update for a period of time; and executing, by thefirst compute node, at least one of the plurality of workloads duringthe period of time.
 2. The computing cluster of claim 1, wherein the oneor more predefined operations comprises a first predefined operation todefer applying the software update to the first compute node for theperiod of time and a second predefined operation to restrict use of thefirst compute node during the period of time, and wherein the firstcomponent comprises at least one of: (i) a firmware of a hardwarecomponent of the first compute node, (ii) a software component of atleast one of the plurality of workloads, (iii) a software componentconfigured to manage the plurality of workloads of the first computenode, and (iv) a first workload, of the plurality of workloads.
 3. Thecomputing cluster of claim 2, wherein the first component comprises thefirst workload, wherein the one or more predefined operations compriseat least one of: (i) disabling the first workload, (ii) altering thefirst workload, and (iii) moving the first workload to a second computenode of the plurality of compute nodes, wherein the second compute nodedoes not violate the compliance rule.
 4. The computing cluster of claim2, wherein the first component comprises the software component of atleast one of the plurality of workloads, wherein the one or morepredefined operations comprise at least one of: (i) uninstalling thesoftware component from the at least one of the plurality of workloads,(ii) disabling the software component from the at least one of theplurality of workloads, (iii) moving the at least one of the pluralityof workloads to a second compute node of the plurality of compute nodes,wherein the second compute node does not violate the compliance rule. 5.The computing cluster of claim 2, wherein the first component comprisesthe firmware of the hardware component of the first compute node,wherein the one or more predefined operations comprise: identifying afirst set of workloads, of the plurality of workloads, that interactwith the hardware component; and moving the first set of workloads to asecond compute node of the plurality of compute nodes, wherein thesecond compute node does not violate the compliance rule, wherein the atleast one of the plurality of workloads executed by the first computenode without applying the software update comprise a second set ofworkloads that do not interact with the hardware component.
 6. Thecomputing cluster of claim 1, wherein the violation of the compliancerule comprises at least one of: (i) executing, by the first computenode, an out of date software module, (ii) executing, by the firstcompute node, a software component that has a security vulnerability,and (iii) executing, by the first compute node, a software componentexperiencing a runtime error.
 7. The computing cluster of claim 1,wherein the first component is determined to violate the compliance rulebased on metadata associated with the software update relative to atleast one attribute of the first component.
 8. The computing cluster ofclaim 1, wherein the one or more predefined operations associated withthe compliance rule are configured to correct the violation of thecompliance rule.
 9. A computer program product comprising: acomputer-readable storage medium having computer-readable program codeembodied therewith, the computer-readable program code executable by oneor more computer processors to perform an operation comprising:determining that a first component on a first compute node, of aplurality of compute nodes in a computing cluster, each of the computenodes comprising at least one processor, violates a compliance rule,wherein the first compute node executes a plurality of workloads,wherein a software update is configured to correct the violation of thecompliance rule by the first component of the first compute node;identifying one or more predefined operations associated with thecompliance rule; and performing the one or more predefined operationswhile deferring applying the software update for a period of time; andexecuting, by the first compute node, at least one of the plurality ofworkloads during the period of time.
 10. The computer program product ofclaim 9, wherein the one or more predefined operations comprises a firstpredefined operation to defer applying the software update to the firstcompute node for the period of time and a second predefined operation torestrict use of the first compute node during the period of time, andwherein the first component comprises at least one of: (i) a firmware ofa hardware component of the first compute node, (ii) a softwarecomponent of at least one of the plurality of workloads, (iii) asoftware component configured to manage the plurality of workloads ofthe first compute node, and (iv) a first workload, of the plurality ofworkloads.
 11. The computer program product of claim 10, wherein thefirst component comprises the first workload, wherein the one or morepredefined operations comprise at least one of: (i) disabling the firstworkload, (ii) altering the first workload, and (iii) moving the firstworkload to a second compute node of the plurality of compute nodes,wherein the second compute node does not violate the compliance rule.12. The computer program product of claim 10, wherein the firstcomponent comprises the software component of at least one of theplurality of workloads, wherein the one or more predefined operationscomprise at least one of: (i) uninstalling the software component fromthe at least one of the plurality of workloads, (ii) disabling thesoftware component from the at least one of the plurality of workloads,(iii) moving the at least one of the plurality of workloads to a secondcompute node of the plurality of compute nodes, wherein the secondcompute node does not violate the compliance rule.
 13. The computerprogram product of claim 10, wherein the first component comprises thefirmware of the hardware component of the first compute node, whereinthe one or more predefined operations comprise: identifying a first setof workloads, of the plurality of workloads, that interact with thehardware component; and moving the first set of workloads to a secondcompute node of the plurality of compute nodes, wherein the secondcompute node does not violate the compliance rule, wherein the at leastone of the plurality of workloads executed by the first compute nodewithout applying the software update comprise a second set of workloadsthat do not interact with the hardware component.
 14. The computerprogram product of claim 9, wherein the first component is determined toviolate the compliance rule based on metadata associated with thesoftware update relative to at least one attribute of the firstcomponent, wherein the violation of the compliance rule comprises atleast one of: (i) executing, by the first compute node, an out of datesoftware module, (ii) executing, by the first compute node, a softwarecomponent that has a security vulnerability, and (iii) executing, by thefirst compute node, a software component experiencing a runtime error.